home *** CD-ROM | disk | FTP | other *** search
- Path: grafix.xs4all.nl!john.hendrikx
- Date: Fri, 26 Jan 96 21:04:49 GMT+1
- Newsgroups: comp.sys.amiga.programmer
- Distribution: world
- Subject: Re: BeBox Is Here. Listen Closely ESCO
- MIME-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- From: john.hendrikx@grafix.xs4all.nl (John Hendrikx)
- Message-ID: <john.hendrikx.49rj@grafix.xs4all.nl>
- Organization: Grafix Attack BBS Holland
-
- In a message of 26 Jan 96 Mjp3783@alpha.isc.rit.e wrote to all:
-
- >> Who says? Maybe Be was 'smart' and told you that 5 MB is the minimum to
- >> get the thing working at a reasonable level, like 1 or 2MB is on the Amiga
- >> (my Amiga won't boot with less than 2MB). If you 'strip' down the Be, run
- >> in 1-bit 320x200 screens, remove all the external hardware except for a
- >> floppy drive you might get it boot in 2MB as well. It is silly however to
- >> except the BeBox to boot in 2MB, just like it is silly to expect a Amiga
- >> to be usefull when you've only got 512K in it.
-
- Mai> Be loses alot of its memory from the fact that the whole OS resides in
- Mai> ROM. I think that 4-8 meg is the most a normal user (not rendering
- Mai> lightwave anims or somesuch) probably needs right now.
-
- On Amiga 4-8 MB is sufficient yes, on Windows NT, Win95, BeOS, OS/2, System 7,
- and most other modern OS-es, NO WAY! I would recommend atleast 16 MB for any of
- the OS-es I just listed, and if you want to get that 'Amiga' feeling of having
- tons of memory free then I would recommend getting 32 MB or more.
-
- >> Mvi> Resource tracking and memory protection could be added in less than
- >> Mvi> 5k.
-
- >> Oh sure, 5K, but that's just counting the code-size.
-
- Mai> OK. Throw in another 16k for tables. Still not huge.
-
- How about all the code for parameter checking (mem-protection is useless
- without parameter checking)? And all the memory needed to actually track the
- resources allocated and who is currently allowed to use them. There is also
- memory wasted because the MMU can only handle memory in 4 or 8K pages. And
- then we still got the MMU tables, one MMU table per program (rebuilding the
- table for every task-switch is not a good idea I think).
-
- >> Of course the Amiga needs VMEM, the reason that I (even if I were the
- >> only one) use it from time to time is proof that the *need* exists, even
- >> on Amiga. You can't expect me to buy 16 MB of extra RAM for the 5
- >> minutes/week I actually NEED that amount of RAM.
-
- Mai> I still disagree here, for the most part. Most people don't have
- Mai> radically changing ram needs - they need a little (almost everyone) or
- Mai> alot (rendering, etc). I think that vm is the wave of the past.
-
- But what's the point of not having VM at all? VM is definitely not a wave of
- the past, not before RAM prices drop to a quarter of the current level. There
- will always be programs requiring more memory than you can afford, always.
-
- >> I don't want to see apps keeping memory usage down at the expense of
- >> features like is happening now. They are actually LIMITING the programs
- >> so they run on 1MB or 2MB Amiga's.
-
- Mai> I am not aware of anything like that happening - most programs grow
-
- Of course you're not aware of that, but it is happening, it's only logical that
- the people of Final Writer will do their best to keep their program running on
- a 1MB or 2MB machine, or else they won't sell their program anymore. That means
- they simply can't add certain features.
-
- What about games? They surely are limited, look at all the pc-ports and how
- they are stripped down from literaly everything (graphics, animations, sounds,
- CPU intensive stuff) JUST so they can run in 2 MB of memory on the slow
- 68020/14 found in the A1200.
-
- Same goes for pure Amiga games, they definitely would have made use of an 68040
- and 10 MB of RAM IF it was the standard, it is not so they limit themselves to
- what IS the standard.
-
- Mai> normally. Pagestream 3.0, for example, has an executable of over 1 meg.
- Mai> I would like to see a trend toward more ... careful programming where
- Mai> people think about code size and memory usage instead of spending
-
- This is AMIGA for god's sake, people already program that way for YEARS, and
- you know why? Because Amiga's are the only computers which STILL come with
- only 2 MB standard. Amiga IS the most efficient computer out there already,
- what the hell more could you want?
-
- Mai> resources like the US congress. I would not want to see useful features
- Mai> cut out either, though.
-
- Amiga is probably the computer who uses the smallest amount of CPU power, and
- the least amount of memory compared to the features it offers. If there is ANY
- computer which can afford to 'waste' a bit of memory than it is Amiga. I can't
- believe that of all people in the world Amiga people are the ones complaining
- about programs using too much memory! Are we really so poor that we can't
- afford even 4 MB of extra memory? Or maybe we are just too damn greedy...
-
- >> Mvi> It does to me. 5 out of the initial 16 mb down the tubes just for
- >> the Mvi> OS? Win95 all over again...
-
- >> You still think in Amiga terms. What if we were to compare Amiga to the
- >> C-64, hmm? C-64 user: "Damn, this Amiga
- >> -requires- a 512K ROM and a whopping 200K to BOOT at minimum (ie. 700K+)!
- >> Boy am I glad I use my C-64 which only eats about 30K orso and leaves the
- >> 38911 other bytes free for my use!"
-
- Mai> But the Amiga offers large numbers of services for the rom/ram space
- Mai> that it takes up. The C64 offered almost no system services.
-
- And BeOS doesn't offer any extra services?
-
- >> Do you have any idea WHY Amiga's need so much more memory than a C-64?
- >> Where
-
- Mai> Yes, I do. In addition to having (almost) a BS in CS, 7 years of AMiga
- Mai> experience and 3-4 years on the C64 before that, I might have some
- Mai> marginal familiarity with those two systems...
-
- >> does all that space go? Name me a few things if you like. If you
- >> figured it out, than apply this to the BeBox and you'll see what I mean.
-
- Mai> Nope. I have seen the Be web site and the features that were above and
- Mai> beyond AmigaOS were not THAT impressive to require a 5x larger os.
-
- The fact that they are not that impressive to you says nothing about how much
- memory these features require. I think that things like a portable OS, which
- is compiled in RISC, Multiprocessing, Resource tracking, RTG, VM and memory
- protection can make a HUGE difference.
-
- Memory protection for example can not be implemented in 5K of code, not even
- close, that is if you want to do it right. Adding decent memory protection
- means parameter checking at the start of almost every OS function for example.
-
- >> The BeBox is a different machine, a next generation machine. It has a
- >> RISC-OS, it doesn't use crappy 2-bit 640x200 screens as standard, it's got
- >> all the features AmigaOS has and many more...
-
- Mai> That is the most unfair comparison I have ever seen. 2 bit 640x200
- Mai> screens are the minimum system for AmigaOS, not the standard. Windows
-
- Oh come on, there are very few people who run an Amiga in the resolutions BeBox
- and most clones run at *minimum*. How many Amiga's run in 640x480 with 16
- colors? Not much as it requires a 31 KHz monitor and an AGA machine or
- gfx-card. On ECS with a FlickerFixer this resolution is useless as it is
- dog-slow, so practically no-one uses it.
-
- Mai> ships to boot up in VGA mode, not the driver for your system. Big deal.
- Mai> BeBox didn't impress me in general. The price was fair, but I just had
- Mai> a bad taste in my mouth about it.
-
- The price isn't just fair, it is competitive with the clones, maybe not the
- dirt-cheap ones with no brand-name behind them but then again BeBox is not a
- 'no-brand' machine either.
-
- >> Things like that take space, not only code-space (and RISC code is
- >> generally a lot bigger too) but what about having to store 24-bit Icons in
- >> memory, and having a 640x480 24-bit screen as standard and stuff like
- >> that. Also parts of windows overlapping will take much more to store when
- >> running in 24-bit, and so on...
-
- Mai> Actually, I have written risc code. 1.5x 680x0 code, roughly. Yes,
- Mai> 24bit imagery will take up more speed (and space) and this is a good
- Mai> arguement for not using it, IMNSHO. 256 color is more than sufficient
-
- But you can't deny that BeBox uses 24-bit imagery and RISC code which drive up
- its memory requirements, just like it will drive up the memory requirements of
- AmigaOS once it has matured as the other OS-es.
-
- Mai> for most people, really.
-
- Sure 256 colors is enough for 99% of us poor old Amiga users who would be
- -extremely- happy even if they could run Workbench in 640x512 with 16 colors at
- a decent pace, let alone 256 colors. In the clone world 256 colors is however
- rapidly becoming the minimum (infact, I think it already is the minimum).
-
- Grtz John
-
- -----------------------------------------------------------------------
- John.Hendrikx@grafix.xs4all.nl TextDemo/FastView/Etc... development
- -----------------------------------------------------------------------
- -- Via Xenolink 1.985B3, XenolinkUUCP 1.1
-